A Model-Driven Approach for the Design, Implementation, and Execution of Software Development Methods

[EN] Software development projects are diverse in nature. For this reason, software companies are often forced to define their methods in-house. In order to define methods efficiently and effectively, software companies require systematic solutions that are built upon sound methodical foundations. Providing these solutions is the main goal of the Method Engineering discipline. Method Engineering is the discipline to design, construct, and adapt methods, techniques, and tools for the development of information systems. Over the last two decades, a lot of research work has been performed in this area. However, despite its potential benefits, Method Engineering is not widely used in industrial settings. Some of the causes of this reality are the high theoretical complexity of Method Engineering and the lack of adequate software support. In this thesis, we aim to mitigate some of the problems that affect Method Engineering by providing a novel methodological approach that is built upon Model-Driven Engineering (MDE) foundations. The use of MDE enables a rise in abstraction, automation, and reuse that allows us to alleviate the complexity of our Method Engineering approach. Furthermore, by leveraging MDE techniques (such as metamodeling, model transformations, and models at runtime), our approach supports three phases of the Method Engineering lifecycle: design, implementation, and execution. This is unlike traditional Method Engineering approaches, which, in general, only support one of these phases. In order to provide software support for our proposal, we developed a Computer-Aided Method Engineering (CAME) environment that is called MOSKitt4ME. To ensure that MOSKitt4ME offered the necessary functionality, we identified a set of functional requirements prior to developing the tool. Then, after these requirements were identified, we defined the architecture of our CAME environment, and, finally, we implemented the architecture in the context of Eclipse. The thesis work was evaluated by means of a study that involved the participation of end users. In this study, MOSKitt4ME was assessed by means of the Technology Acceptance Model (TAM) and the Think Aloud method. While the TAM allowed us to measure usefulness and ease of use in a subjective manner, the Think Aloud method allowed us to analyze these measures objectively. Overall, the results were favorable. MOSKitt4ME was highly rated in perceived usefulness and ease of use; we also obtained positive results with respect to the users' actual performance and the difficulty experienced.[ES] Los proyectos de desarrollo de software son diversos por naturaleza. Por este motivo, las compañías de software se ven forzadas frecuentemente a definir sus métodos de manera interna. Para poder definir métodos de forma efectiva y eficiente, las compañías necesitan soluciones sistemáticas que estén definidas sobre unos fundamentos metodológicos sólidos. Proporcionar estas soluciones es el principal objetivo de la Ingeniería de Métodos. La Ingeniería de Métodos es la disciplina que aborda el diseño, la construcción y la adaptación de métodos, técnicas y herramientas para el desarrollo de sistemas de información. Durante las dos últimas décadas, se ha llevado a cabo mucho trabajo de investigación en esta área. Sin embargo, pese a sus potenciales beneficios, la Ingeniería de Métodos no se aplica ampliamente en contextos industriales. Algunas de las principales causas de esta situación son la alta complejidad teórica de la Ingeniería de Métodos y la falta de un apropiado soporte software. En esta tesis, pretendemos mitigar algunos de los problemas que afectan a la Ingeniería de Métodos proporcionando una propuesta metodológica innovadora que está basada en la Ingeniería Dirigida por Modelos (MDE). El uso de MDE permite elevar el nivel de abstracción, automatización y reuso, lo que posibilita una reducción de la complejidad de nuestra propuesta. Además, aprovechando técnicas de MDE (como por ejemplo el metamodelado, las transformaciones de modelos y los modelos en tiempo de ejecución), nuestra aproximación da soporte a tres fases del ciclo de vida de la Ingeniería de Métodos: diseño, implementación y ejecución. Esto es a diferencia de las propuestas existentes, las cuales, por lo general, sólo dan soporte a una de estas fases. Con el objetivo de proporcionar soporte software para nuestra propuesta, implementamos una herramienta CAME (Computer-Aided Method Engineering) llamada MOSKitt4ME. Para garantizar que MOSKitt4ME proporcionaba la funcionalidad necesaria, definimos un conjunto de requisitos funcionales como paso previo al desarrollo de la herramienta. Tras la definción de estos requisitos, definimos la arquitectura de la herramienta CAME y, finalmente, implementamos la arquitectura en el contexto de Eclipse. El trabajo desarrollado en esta tesis se evaluó por medio de un estudio donde participaron usuarios finales. En este estudio, MOSKitt4ME se evaluó por medio del Technology Acceptance Model (TAM) y del método Think Aloud. Mientras que el TAM permitió medir utilidad y facilidad de uso de forma subjetiva, el método Think Aloud permitió analizar estas medidas objetivamente. En general, los resultados obtenidos fueron favorables. MOSKitt4ME fue valorado de forma positiva en cuanto a utilidad y facilidad de uso percibida; además, obtuvimos resultados positivos en cuanto al rendimiento objetivo de los usuarios y la dificultad experimentada.[CA] Els projectes de desenvolupament de programari són diversos per naturalesa. Per aquest motiu, les companyies es veuen forçades freqüenment a definir els seus mètodes de manera interna. Per poder definir mètodes de forma efectiva i eficient, les companyies necessiten solucions sistemàtiques que estiguin definides sobre uns fundaments metodològics sòlids. Proporcionar aquestes solucions és el principal objectiu de l'Enginyeria de Mètodes. L'Enginyeria de Mètodes és la disciplina que aborda el diseny, la construcció i l'adaptació de mètodes, tècniques i eines per al desenvolupament de sistemes d'informació. Durant les dues últimes dècades, s'ha dut a terme molt de treball de recerca en aquesta àrea. No obstant, malgrat els seus potencials beneficis, l'Enginyeria de Mètodes no s'aplica àmpliament en contextes industrials. Algunes de les principals causes d'aquesta situació són l'alta complexitat teòrica de l'Enginyeria de Mètodes i la falta d'un apropiat suport de programari. En aquesta tesi, pretenem mitigar alguns dels problemes que afecten a l'Enginyeria de Mètodes proporcionant una proposta metodològica innovadora que està basada en l'Enginyeria Dirigida per Models (MDE). L'ús de MDE ens permet elevar el nivell d'abstracció, automatització i reutilització, possibilitant una reducció de la complexitat de la nostra proposta. A més a més, aprofitant tècniques de MDE (com per exemple el metamodelat, les transformacions de models i els models en temps d'execució), la nostra aproximació suporta tres fases del cicle de vida de l'Enginyeria de Mètodes: diseny, implementació i execució. Açò és a diferència de les propostes existents, les quals, en general, només suporten una d'aquestes fases. Amb l'objectiu de proporcionar suport de programari per a la nostra proposta, implementàrem una eina CAME (Computer-Aided Method Engineering) anomenada MOSKitt4ME. Per garantir que MOSKitt4ME oferia la funcionalitat necessària, definírem un conjunt de requisits funcionals com a pas previ al desenvolupament de l'eina. Després de la definició d'aquests requisits, definírem la arquitectura de l'eina CAME i, finalment, implementàrem l'arquitectura en el contexte d'Eclipse. El treball desenvolupat en aquesta tesi es va avaluar per mitjà d'un estudi on van participar usuaris finals. En aquest estudi, MOSKitt4ME es va avaluar per mitjà del Technology Acceptance Model (TAM) i el mètode Think Aloud. Mentre que el TAM va permetre mesurar utilitat i facilitat d'ús de manera subjectiva, el mètode Think Aloud va permetre analitzar aquestes mesures objectivament. En general, els resultats obtinguts van ser favorables. MOSKitt4ME va ser valorat de forma positiva pel que fa a utilitat i facilitat d'ús percebuda; a més a més, vam obtenir resultats positius pel que fa al rendiment objectiu dels usuaris i a la dificultat experimentada.Cervera Úbeda, M. (2015). A Model-Driven Approach for the Design, Implementation, and Execution of Software Development Methods [Tesis doctoral no publicada]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/53931TESI

Treatment with tocilizumab or corticosteroids for COVID-19 patients with hyperinflammatory state: a multicentre cohort study (SAM-COVID-19)

Objectives: The objective of this study was to estimate the association between tocilizumab or corticosteroids and the risk of intubation or death in patients with coronavirus disease 19 (COVID-19) with a hyperinflammatory state according to clinical and laboratory parameters. Methods: A cohort study was performed in 60 Spanish hospitals including 778 patients with COVID-19 and clinical and laboratory data indicative of a hyperinflammatory state. Treatment was mainly with tocilizumab, an intermediate-high dose of corticosteroids (IHDC), a pulse dose of corticosteroids (PDC), combination therapy, or no treatment. Primary outcome was intubation or death; follow-up was 21 days. Propensity score-adjusted estimations using Cox regression (logistic regression if needed) were calculated. Propensity scores were used as confounders, matching variables and for the inverse probability of treatment weights (IPTWs). Results: In all, 88, 117, 78 and 151 patients treated with tocilizumab, IHDC, PDC, and combination therapy, respectively, were compared with 344 untreated patients. The primary endpoint occurred in 10 (11.4%), 27 (23.1%), 12 (15.4%), 40 (25.6%) and 69 (21.1%), respectively. The IPTW-based hazard ratios (odds ratio for combination therapy) for the primary endpoint were 0.32 (95%CI 0.22-0.47; p < 0.001) for tocilizumab, 0.82 (0.71-1.30; p 0.82) for IHDC, 0.61 (0.43-0.86; p 0.006) for PDC, and 1.17 (0.86-1.58; p 0.30) for combination therapy. Other applications of the propensity score provided similar results, but were not significant for PDC. Tocilizumab was also associated with lower hazard of death alone in IPTW analysis (0.07; 0.02-0.17; p < 0.001). Conclusions: Tocilizumab might be useful in COVID-19 patients with a hyperinflammatory state and should be prioritized for randomized trials in this situatio

A Model-Driven approach for the design and implementation of software development methods

The Situational Method Engineering (SME) discipline emerged two decades ago to address the challenge of the in-house definition of software development methods and the construction of the corresponding supporting tools. Unfortunately, current SME approaches still have limitations that are hindering their adoption by industry. One of these limitations is that most approaches do not properly encompass two phases of the SME lifecycle, which refer to the method design and the method implementation. To address this limitation, this paper demonstrates how Model-Driven Development (MDD) techniques can contribute to successfully cover both phases. The proposal is illustrated by a real case study that is currently being used at the Valencian Regional Ministry of Infrastructure, Territory and Environment.Cervera Úbeda, M.; Albert Albiol, M.; Torres Bosch, MV.; Pelechano Ferragud, V. (2012). A Model-Driven approach for the design and implementation of software development methods. International Journal of Information System Modeling and Design. 3(4):86-103. doi:10.4018/jismd.2012100105S8610334Arni-Bloch, N. (2005). Towards a CAME tools for situational method engineering. In Proceedings of the 1st International Conference on Interoperability of Enterprise Software and Applications.Atkinson, C., & Kuhne, T. (2003). Model-driven development: a metamodeling foundation. IEEE Software, 20(5), 36-41. doi:10.1109/ms.2003.1231149Brinkkemper, S. (1996). Method engineering: engineering of information systems development methods and tools. Information and Software Technology, 38(4), 275-280. doi:10.1016/0950-5849(95)01059-9Brinkkemper, S., Saeki, M., & Harmsen, F. (1999). Meta-modelling based assembly techniques for situational method engineering. Information Systems, 24(3), 209-228. doi:10.1016/s0306-4379(99)00016-2Cervera, M., Albert, M., Torres, V., Pelechano, V., Bonet, B., & Cano, J. (2010). A technological framework to support model driven method engineering. In Actas de los Talleres de las Jornadas de Ingeniera del Software y Bases de Datos (pp. 47-56).Ferguson, R. ., Parrington, N. ., Dunne, P., Hardy, C., Archibald, J. ., & Thompson, J. . (2000). MetaMOOSE—an object-oriented framework for the construction of CASE tools. Information and Software Technology, 42(2), 115-128. doi:10.1016/s0950-5849(99)00081-6Grundy, J. C., & Venable, J. R. (1996). Towards an integrated environment for method engineering. In Proceedings of the IFIP TC8, WG8.1/8.2 Working Conference on Method Engineering (pp. 45-62).Gupta, D., & Prakash, N. (2001). Engineering Methods from Method Requirements Specifications. Requirements Engineering, 6(3), 135-160. doi:10.1007/s007660170001Harmsen, A. F. (1997). Situational method engineering (Unpublished doctoral dissertation). Utrecht, The Netherlands: University of Twente.Hevner, March, Park, & Ram. (2004). Design Science in Information Systems Research. MIS Quarterly, 28(1), 75. doi:10.2307/25148625Heym, M., & Osterle, H. (1992). A semantic data model for methodology engineering. In Proceedings of the 5th International Workshop on Computer-Aided Software Engineering (pp. 142-155).Karlsson, F., & Ågerfalk, P. (2009). Exploring agile values in method configuration. European Journal of Information Systems, 18(4), 300-316. doi:10.1057/ejis.2009.20Kelly, S., Lyytinen, K., & Rossi, M. (1996). MetaEdit+ A fully configurable multi-user and multi-tool CASE and CAME environment. In P. Constantopoulos, J. Mylopoulos, & Y. Vassiliou (Eds.), Proceedings of the 8th International Conference on Advanced Information Systems Engineering (LNCS 1080, pp. 1-21).Mathiassen, L. (2002). Collaborative practice research. Information Technology & People, 15(4), 321-345. doi:10.1108/09593840210453115Mirbel, I., & Ralyté, J. (2005). Situational method engineering: combining assembly-based and roadmap-driven approaches. Requirements Engineering, 11(1), 58-78. doi:10.1007/s00766-005-0019-0Niknafs, A., & Asadi, M. (2009). Towards a process modeling language for method engineering support. In Proceedings of the WRI World Congress on Computer Science and Information Engineering (pp. 674-681).Niknafs, A., & Ramsin, R. (2008). Computer-aided method engineering: An analysis of existing environments. In Z. Bellahsène & M. Léonard (Eds.), Proceedings of the 20th International Conference on Advanced Information Systems Engineering (LNCS 5074, pp. 525-540).Object Management Group. (2005). Reusable asset specification (v2.2). Retrieved from http://www.omg.org/spec/RAS/Object Management Group. (2007). Software & systems process engineering metamodel (v2.0). Retrieved from http://www.omg.org/spec/SPEM/2.0/Object Management Group. (2011). Business process model and notation (v2.0). Retrieved from http://www.omg.org/spec/BPMN/2.0/Prakash, N. (1997). Towards a formal definition of methods. Requirements Engineering, 2(1), 23-50. doi:10.1007/bf02802896Ralyté, J., Deneckère, R., & Rolland, C. (2003). Towards a generic model for situational method engineering. In J. Eder & M. Missikoff (Eds.), Proceedings of the 15th International Conference on Advanced Information Systems Engineering (LNCS 2681, p. 1029).Rolland, C., Prakash, N., & Benjamen, A. (1999). A Multi-Model View of Process Modelling. Requirements Engineering, 4(4), 169-187. doi:10.1007/s007660050018Saeki, M. (2003). CAME: The first step to automated method engineering. In Proceedings of the Workshop on Process Engineering for Object-Oriented and Component-Based Development.Wistrand, K., & Karlsson, F. (2004). Method components – Rationale revealed. In Proceedings of the 16th International Conference on Advanced Information Systems Engineering (pp. 189-201)

Revista electrónica interuniversitaria de formación del profesorado

Monográfico con el título: 'La universidad de la convergencia. Acreditación y certificaciones. Estrategias docentes, tutoriales y evaluadoras de reforma'. Resumen basado en el de la publicaciónEl Espacio Europeo de Educación Superior (EEES) pone el acento en dos cuestiones básicas: el aprendizaje y el trabajo del alumno. Al hilo de ese discurso, se pretende dar a conocer las posibilidades del cuaderno de bitácora como recurso formativo y como instrumento de investigación-acción en el ámbito de la educación universitaria. La bitácora se presenta aquí como un instrumento al servicio de una pedagogía de la esperanza y de la autonomía, frente a la pedagogía de la sumisión, capaz de convertir el aula en un espacio reflexivo, crítico y comunicativo.AragónES